All releases
v2.1.0
17 July 2026
Send failures to PagerDuty
A rule's owner can now name a PagerDuty service, so a failure during an incident reaches the rota instead of a channel nobody is reading at 3am.
Owners have always resolved to a Slack channel. That is the right place for an alert at eleven in the morning and the wrong one for a deploy stopped in the middle of an incident.
An owner can now name a PagerDuty service directly, and a rule can send different things to different places depending on how serious it is.
owner team:payments
tell slack:#payments-platform
page pagerduty:payments-primary when it stops a deployQuiet unless you ask
Nothing pages anyone unless you write the page line. Connecting PagerDuty on its own changes nothing.